Motivation

Sometimes we add code that needs a feature to a Zebra crate, then activate that feature in zebrad. But we forget to activate the feature in the crate that actually contains the code.

For an example, see PR #1365, where individual crates use features in their dependencies, but don't declare those features in their Cargo.toml.

Fixes #1364
Fixes #4550

Designs

• Build each Zebra crate individually in a CI job, including Zebra's custom Tower crates
• Fail the PR if any build fails.

Solution

• Create a specific workflow to accomplish this task
• Use a matrix strategy to have a separate job for each crate, with individual logs
• Keep a fail-fast strategy, as we don't want to keep consuming minutes if a crate build failed

Review

Not ready

Reviewer Checklist

• Code implements Specs and Designs
• Tests for Expected Behaviour
• Tests for Errors

Follow Up Work

It would be better to generate the crate names automatically, but this task would need further analysis to be able to generate a file with the needed GHA format for a matrix.